Skip to content

feat(browser): provide project reference in ToMatchScreenshotResolvePath#10138

Open
macarie wants to merge 3 commits intovitest-dev:mainfrom
macarie:feat/config-resolve-screenshot-dir
Open

feat(browser): provide project reference in ToMatchScreenshotResolvePath#10138
macarie wants to merge 3 commits intovitest-dev:mainfrom
macarie:feat/config-resolve-screenshot-dir

Conversation

@macarie
Copy link
Copy Markdown
Member

@macarie macarie commented Apr 13, 2026

Description

Resolves #10039

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

  • It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
  • Ideally, include a test that fails without this PR but passes with it.
  • Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
  • Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

  • Run the tests with pnpm test:ci.

Documentation

  • If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

  • Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 13, 2026

Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 6a667b7
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/69e7630e552fa900081081d2
😎 Deploy Preview https://deploy-preview-10138--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Comment on lines +481 to +486
/**
* The project's fully resolved {@link https://vitest.dev/config/|configuration}.
*
* @experimental
*/
config: ResolvedConfig
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if this is the best thing to do or if we should just pick/re-create the instances entry the project is running within 🤔

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would just pass down project, we already pass it down for global setup

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that would be more consistent. Should I keep the @experimental tag?

@macarie macarie changed the title feat(browser): provide resolved config in ToMatchScreenshotResolvePath feat(browser): provide project reference in ToMatchScreenshotResolvePath Apr 14, 2026
@macarie macarie marked this pull request as ready for review April 21, 2026 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Screenshot filenames do not take instance names into account

2 participants